bind address ip_address [ nexthop-forwarding-address nexthop_ip_address [ mpls-label input in_mpls_label_value output out_mpls_label_value1 [ out_mpls_label_value2 ] ] ]
no bind address ip_address
address ip_address
Specifies the IP address of an interface in the current context through which the communication with the DHCP server occurs. ip_address must be expressed in IPv4 dotted-decimal notation.
nexthop-forwarding-address nexthop_ip_address
Specifies the next hop gateway address for in MPLS network to which the packets with MPLS labels will be forwarded. nexthop_ip_address must be expressed in IPv4 dotted-decimal or IPv6 colon-separated notation.
mpls-label input in_mpls_label_value
Specifies the MPLS label to identify inbound traffic destined for the configured DHCP service bind address ip_address.
in_mpls_label_value is the MPLS label that will identify inbound traffic destined for the configured DHCP service and must be an integer from 16 through 1048575.
Important: This keyword is license-enabled and available with valid MPLS feature license only.
Caution: For DHCP over MPLS feature to work in StarOS 9.0 onward the dhcp ip vrf command must be configured in DHCP service. Without dhcp ip vrf command the DHCP service using MPLS labels will not be started as a part of a DHCP over MPLS configuration. In StarOS 9.0 onward this keyword is a critical parameter for the DHCP-Service. Any change in its value will result in DHCP-service restart and clearing of the existing calls.Adds the MPLS label to the outbound traffic sent from the configured DHCP service bind address ip_address. The labels out_mpls_label_value1 and out_mpls_label_value2 identify the MPLS labels to be added to packets sent from the specified dhcp service bind address.
out_mpls_label_value1 is the inner output label and must be an integer from 16 through 1048575.
out_mpls_label_value2 is the outer output label and must be an integer from 16 through 1048575.
Important: This keyword is license-enabled and available with valid MPLS feature license only.For DHCP over MPLS feature to work in StarOS 9.0 onward dhcp ip vrf command must be configured in DHCP service. Without dhcp ip vrf command the DHCP service using MPLS labels will not be started.
Caution: As a part of DHCP over MPLS configuration, the mpls-label input keyword in the bind address command is also a critical parameter for the DHCP-Service. Any change in its value will result in DHCP-service restart and clearing of the existing calls.|
•
|
deadtime: Default 10 minutes
|
|
•
|
detect-dead-server { consecutive-failures }: Default 5
|
|
•
|
server-selection-algorithm: Default First-server
|
Important: The chaddr information value in the DHCPACK message will be parsed but not be validated against the value maintained with client. The chaddr information value in DHCPACK will be ignored and not be stored internally.
Important: This keyword is GGSN license controlled.dhcp deadtime max_time
Specifies the maximum amount of time (in minutes) to wait before communicating with a DHCP server that was previously unreachable. max_time is an integer value from 1 through 65535. Default: 10
Important: If all DHCP servers are down, the system will immediately treat all DHCP servers as active, regardless of the deadtime that is specified.Refer to the dhcp detect-dead-server and max-retransmissions commands for additional information on the process the system uses to mark a server as down.
The following command configures the system to wait 20 minutes before attempting to re-communicate with a dhcp server that was marked as down:
dhcp detect-dead-server consecutive-failures max_number
consecutive-failures max_number
This command works in conjunction with the max-retransmissions parameter to set a limit to the number of communication failures that can occur with a configured DHCP server.
The max-retransmissions parameter limits the number of attempts to communicate with a server. Once that limit is reached, the system treats it as a single failure. This parameter limits the number of consecutive failures that can occur before the system marks the server as down and communicate with the server of next highest priority.
The following command configures the system to allow 8 consecutive communication failures with a DHCP server before it marks it as down:
dhcp ip vrf vrf_name
Specifies the name of a pre-configured VRF context instance to be associated with a DHCP service. vrf_name is the name of a pre-configured VRF context configured in Context Configuration mode and associated with the IP Pool used by the DHCP service.
By default the VRF is NULL, which means that DHCP service is bound with binding address given by bind address command only.
Caution: As a part of this configuration the mpls-label input keyword in the bind address command is also a critical parameter for the DHCP-Service. Any change in its value will result in DHCP-service restart and clearing of the existing calls.Following command associates VRF context instance dhcp_vrf1 with this DHCP service:
no dhcp server ip_address
priority priority
Specifies the priority of the server if multiple servers are configured. priority is an integer from 1 through 1000. 1 is the highest priority.
Important: If a server is removed, all calls having an IP address allocated from the server will be released.The following command configures a DHCP server with an IP address of 192.168.1.200 and a priority of 1:
min min_time
max max_time
When half of the lease time has expired, the system automatically requests a lease renewal from the DHCP server. This is configured using the T1-threshold command.
The following command configures the minimum allowable lease time for the system to be 1000 and the maximum to be 36000:
max-retransmissions max_number
Specifies the maximum number of re-attempts the system tries when no response is received from a DHCP server. max_number is an integer from 1 through 20. Default: 5
This command works in conjunction with the dhcp detect-dead-server parameter to set a limit to the number of communication failures that can occur with a configured DHCP server.
When the value specified by this parameter is met, a failure is logged. The dhcp detect-dead-server parameter specifies the number of consecutive failures that could occur before the server is marked as down.
In addition, the retransmission-timeout command controls the amount of time between re-tries.
Specifies the time that the system waits (in milliseconds) before reattempting communication with the DHCP server. time is an integer from 100 through 20000. Default: 10000
This command works in conjunction with the max-retransmissions command to establish a limit on the number of times that communication with a DHCP server is attempted before a failure is logged.
The following command configures a retry timeout of 1000 milliseconds:
T1-threshold percentage
Specifies the percentage of the allocated IP address lease time at which the DHCP call-line state is changed to “RENEWING”. percentage is an integer from 40 through 66. Default: 50
This command is used to identify the time at which a subscriber must renew their DHCP lease as a percentage of the overall lease time. (Refer to the lease-duration command in this chapter for information on configuring the IP address lease period.)
T2-threshold percentage
Specifies the percentage of the allocated IP address lease time at which the DHCP call-line state is changed to “REBINDING”. percentage is an integer from 67 through 99. Default: 88
This command is used to identify the time at which a subscriber re-binds their DHCP leased IP address as a percentage of the overall lease time. (Refer to the lease-duration command in this chapter for information on configuring the IP address lease period.)
